5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

RUN


The RUN statement transfers processing control from the current process to an external program.

    ????? RUN      ??? ?????????????????????? ???              END? ?  FAIL ?
    (1)            (2) (3)                    (4)                  (5)     (6)

(1) T/F execution conditions
(2) Application ID
(3) Program name or field containing it
(4) Occurrence (constant/index)
(5) End current process first? (Y/N)
(6) Fail action (0=nothing, 1=warning, 2=error, 3=cancel)

Sets True/False Status Indicator

If the designer specifies that a RUN is not required and the invocation fails, the next true/false flag is set to F. If the invoked process completes successfully, the next true/false flag is set to T. If the process cannot be invoked successfully, the FAIL parameter determines what additional action to take.

Using the Statement

RUN is used to invoke an external program in the same way that it would be invoked from the operating system command processor. As parameters are passed using the PASS statement, they are assigned a number. Each parameter can be referred to in the command line by using dollar sign ($) plus the parameter number. Using dollar sign ($) plus * refers to any unused remaining parameters. If no dollar signs ($) are used, APPX ignores all parameters. If you need to use a dollar sign ($) in the command line, precede it with a backslash (\). On the DOS platform, use ~ (tilde).

The END? parameter is presently ignored.

If you PASS a file to the RUN statement, APPX supplies the full operating system path name.

The value returned from a RUN function is put in the four-byte binary predefined field RETURN CODE.

Passing Values

The RUN statement passes the current PASS list, if any. Refer to the PASS Lists section for details.

Related PDFs

RETURN CODE

Related Statements

CALL, PASS

Example

In the following example, RUN is used to invoke the operating system's 'display' utility. The name of this program is stored in the field OS DISPLAY UTILITY in application ABC. 

          RUN      ABC OS DISPLAY UTILITY                      END? Y  FAIL 3

Application Design Manual                                         "Powered by Appx Software"

687

©2006 By APPX Software, Inc. All Rights Reserved